home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ShareWare OnLine 2
/
ShareWare OnLine Volume 2 (CMS Software)(1993).iso
/
virus
/
vc50_jan.zip
/
TECHREF.DOC
< prev
next >
Wrap
Text File
|
1993-01-24
|
9KB
|
291 lines
Victor Charlie Ver 5.0
Technical Summary Reference
This file is a no-frills summary of technical information about use of
Victor Charlie. It may be handy for those who like to "do it by hand"
with their own batch or shell programs, or directly from the command
line.
COMMAND LINE ARGUMENTS
Initialization Only:
VC1 [DEMO][HELP][-][newVSIGname] [newHELPname]
|---set VCHECK to no "intelligence" in case of False Alarms
Initialization MUST be done in this sequence:
COPY VC1 VC1.COM
VC1
copy vc1 vc1.bin (to save your initialized version)
COPY VC2 VC2.EXE
COPY VCHECK VCHECK.COM
COPY VCOMP VCOMP.COM
COPY VC VC.EXE
copy vc.bin vcbin (optional, save a backup)
GET, PTRESQ, and BOOTFIX are not part of the initialization
process. They can be made into executable files at any time, e.g.
COPY BOOTFIX BOOTFIX.COM
===/===/===/===
Post-Initialization (normal, daily) use:
VC1 [HUSH][DEMO][HELP]
VC2 [HUSH][DEMO][HELP]
VCHECK [HUSH][ONLY][HELP][DEMO][.][-][/outfile][D ][filespec (filespec...)]
VCOMP [file1 file2]
===/===/===/===
ERRORCODE Returns
VC.EXE:
0 = OK
1 = WRONG DOS VERSION (if 2.0, no return if 1.x)
2 = COULD NOT FIND MYSELF
3 = NOT INITIALIZED BY VC1
4 = MEMORY ALLOCATION ERROR
5 = VC.BIN BAD (BITCHECK FAILED OR COULD NOT RUN OR MISSING)
9 = VIRUS DETECTED, FILE INFECTOR
13 = 4 + 9 ABOVE
VC1.COM:
0 = OK
1 = WRONG DOS VERSION (if 2.0, no return if 1.x)
2 = COULD NOT FIND MYSELF
3 = UNSAFE/BAD INITIALIZATION CONDITON
4 = MEMORY ALLOCATION ERROR
5 = EFFECTIVE MEMORY CHANGE (MEMORY PARASITE)
6 = BAD FILE FOUND IN VC1.CFG (MAGIC1)
7 = VIRUS DETECTED, BOOT INFECTOR
9 = VIRUS DETECTED, FILE INFECTOR
10 = BAD FILE FOUND IN VC1.CFG QUALIFIED TO ATTEMPT A SIG CAPTURE
(EXE OR COM < 64K) (MAGIC2)
13 = magic1 + boot
15 = magic1 + file
16 = boot + file
17 = boot + magic2
19 = file + magic2
22 = magic1 + boot + file
26 = boot + file + magic2
VC2.EXE
0 = OK
1 = WRONG DOS VERSION (if 2.0, no return if 1.x)
2 = COULD NOT FIND MYSELF
3 = NOT INITIALIZED BY VC1
4 = MEMORY ALLOCATION ERROR
9 = VIRUS DETECTED, FILE INFECTOR
VCHECK.COM:
0 = OK
1 = WRONG DOS VERSION (if 2.0, no return if 1.x)
2 = COULD NOT FIND MYSELF
3 = NOT INITIALIZED BY VC1
4 = MEMORY ALLOCATION ERROR
5 = INTERRUPTED BY USER
6 = DID NOT LIKE BOOT SECTOR OF FLOPPY
9 = VIRUS DETECTED, FILE INFECTOR
11, 14, 15, 20 = combinations of 5,6,9 above
VCOMP.COM:
0 = OK
1 = WRONG DOS VERSION (if 2.0, no return if 1.x)
2 = COULD NOT FIND MYSELF
3 = NOT INITIALIZED BY VC1
4 = MEMORY ALLOCATION ERROR
5 = BAD INPUT FILE
6 = STATISTICS SAME IN BOTH LISTS, BUT LISTS DIFFER
7 = SOMETHING IN LIST HAS MISMATCHED STATISTICS
9 = VIRUS DETECTED, FILE INFECTOR
14 = 5 + 9 ABOVE
15 = 6 + 9 ABOVE
16 = 7 + 9 ABOVE
PTRESQ.COM, BOOTFIX.COM:
0 = OK
1 = WRONG DOS VERSION (if 2.0, no return if 1.x)
2 = COULD NOT FIND MYSELF
3 = OTHER FAILURES (See below)
4 = TRIED TO RUN FROM HARD DISK, DELETED
9 = VIRUS DETECTED, FILE INFECTOR
GET.COM
0 - 90 = OK, NORMAL RETURN
201 = WRONG DOS VERSION (if 2.0, no return if 1.x)
202 = COULD NOT FIND MYSELF
203 = ! COMMAND FAILED
209 = VIRUS DETECTED, FILE INFECTOR
(See also GET for other special features and returns)
===/===/===/===
Possible VC1 alarms during Initialization (returns error code 3)
!!! CONDITIONS NOT SAFE TO INITIALIZE VC1 !!!
TROUBLE: Not initializing with clean boot. (Interrupt #)
TROUBLE: (VC.BIN VC VC2 VCHECK VCOMP) file not found.
TROUBLE: Danger in hard disk Partition Sector.
Hit [H] key for help | any other key to quit ==>
...
[H]elp | [F]ix - see warnings | [I]nitialize anyway |
Other key to quit ==>
TROUBLE: Cannot install in network drive.
TROUBLE: Do not install in root of hard disk.
TROUBLE: Bad filename(s) in command line.
TROUBLE: Bad filename(s): 2nd letter of new name must NOT be "B"
TROUBLE: Not enough free memory.
Other programs will generate errorcode 3 if not initialized. They
will display the following message:
!!! THIS PROGRAM HAS NOT BEEN INITIALIZED !!!
Please follow the detailed installation instructions in the manual,
or perform all the steps recommended by the install program.
===/===/===/===
Special alarm messages and Errorcodes:
ALL: EC=1
Must be DOS 3.0 or higher.
ALL: EC=2
(my name) file not found.
ALL: EC=4
Not enough free memory.
VCOMP.COM: EC=5
File specified does not exist or was not made by VCHECK.COM.
VC.EXE: EC=5
(vc.bin) FILE NOT FOUND
COULD NOT EXEC (vc.bin)
PTRESQ: EC=3
RESTORE ATTEMPT FAILED
COULD NOT CREATE C:\PT[n].CPY
COULD NOT READ PARTITION SECTOR
COULD NOT FIND HARD DISK
===/===/===/===
Victor Charlie's resource usage:
These programs are not frugal about memory use. They grab huge
chunks, like 64K file buffers, which is very fast. Here's what they
actually need to function:
VC 128K itself, size of VC.EXE + size of VC.BIN to run
to run VC.BIN.
VC1 256K
VC2 128K
VCHECK 256K
VCOMP 256K
===/===/===/===
Special-case command-line (or batch-file) arguments:
VC1 HUSH
HUSH is ignored for any initialization run of VC1.
It should always be obvious that this special event
is happening.
hush Suppress all display UNTIL something goes wrong;
normal displays thereafter.
VC2 HUSH
hush Suppress all display UNTIL something goes wrong,
normal displays thereafter.
VCHECK HUSH/ONLY
Both of these args are "eaten" by VCHECK, which means
they can PRECEDE any other args. Args must be separated
by a space.
hush Suppress virus check. Suppress non-redirectable
display. In effect you see on the screen what
you'd see in a file you'd redirect to. So if you
redirect, you'll see nothing at all. Screen
display is turned back on (hush turned off) if
the user interrupts the check by hitting a key,
or if VCHECK was self-infected. ("no-start"
messages 1-4 are always displayed, as with the
other programs.)
only This is an independent special argument that
restricts inspection to the current drive and
turns off virus checking. If someone wants to
check only a certain drive for virus, then he
just gives that drive letter on the command
line.
VCOMP
No use of special argument. Normally VCOMP does not display
anything but exceptions and concluding messages if both
file names are given on the command line, and everything
may be redirected anyway.
===/===/===/===
Victor Charlie programs "communicate" with each other during normal,
post-initialization use. Here is a list of "dependent files" upon
which VC relies, and how they interact with each other.
[P] means path and basename of parent.
[N] means current path and basename of parent.
[H] means path of home directory.
The default name of the signature file is [H]\vc.sig.
The default name of the BOOT signature file is [H]\vB.sig.
The default name of the help file is [H]\vc.hlp.
These may be set by the user to ANYTHING by putting new names on
the command line for VC1 at init time:
VC1 newsigname newhelpname
Thereafter the names will be
[H]\newsigname and [H]\newhelpname,
[H]\nBwsigname
CREATES/WRITES LOOKS FOR
VC1 [H]\0??????? (init) [H]\0???????
[H]\1??????? (init) [H]\1???????
[H]\signature-file [H]\help-file
[P].CFG
[H]\VC (init)
[H]\VC1 (init)
[H]\VC2 (init)
[H]\VCHECK (init)
VC2 [H]\signature-file [H]\help-file
VCHECK [P].LOG [N].CFG
[H]\signature-file [P].CFG
[H]\signature-file
[H]\sBgnature-file
[H]\help-file
VC [H]\signature-file [P].BIN
PTRESQ.COM \PT[n].CPY
===/===/===/===